Rename 'master' branch to 'main' #9761
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've replicated our branch protection rule currently on |
auvipy
approved these changes
Aug 14, 2025
|
Thanks both! I'm planning to action this tomorrow around midday |
|
That all done. Folks with a fork will be prompted by GitHub to rename their branch too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To follow the current conventions, as both git and GitHub now default to
main. I think this repo is perhaps the last one where I'm a maintainer and where this is not the case. GitHub has refined the rename workflow a few years back and it's prety painless now, even giving nudges to forks to do the switch.Before merging this, a maintainer will have to go the General settings page and use the "Reanme branch" button (the one with a pencil)